There are two types of configurations of the network hardware lock: 
the setup in the machine where the hardlock is placed (hardlock 
server) and the setup in the machine where the hardlock is connected 
(client): 

 1. Hardware lock server. In this machine, after executing the file 
    'Install network hardware lock server.exe', as specified in the 
    installation instructions, the 'Hardware lock server' window must 
    be minimized (not closed). In this window, you can find on-screen 
    information about the operation of each of the options. 

 2. Client. To access the setup for the client once you are in one of 
    the programs, open the 'Help' menu, then, select 'About...'. The 
    'Permissions' window will drop down; within this window, you must 
    select the 'Network hardware lock configuration' button. Inside 
    this new dialogue, you can find on-screen information information 
    about the operation of each of the options. 

  
CASE 1. The hardware lock is not detected in the machine it is 
connected to. Check that: 

 1. A network card is available. 

 2. The TCP/IP protocol is installed. 

 3. The network hardware lock controller is activated. 

  
CASE 2. The hardware lock is not detected in a client machine. Check 
that: 

 1. In the hardware lock server, the network hardlock controller or 
    driver is activated. 

 2. In the client machine: 
  A network card is available. 

  The TCP/IP protocol is installed. 

  Check that the client machine can see the hardware lock server. For 
   this: 
   -Execute a MS-DOS session. 
   -Type the command: 'ping', followed by the network name of the 
    server machine. You will see a number within brackets and 
    separated by periods. Write this number down; it identifies the 
    machine where the hardware lock is installed. For example, if you 
    type: 'C:\ping server', where 'server' refers to the network name 
    for the computer that has the hardlock installed, you will then 
    see a text similar to: 'Pinging the server [192.168.0.32] with 32 
    bytes of data'. 
   -If the hardlock server cannot be seen, it could be because the IP 
    addresses of both machines are not compatible. In this case, 
    obtain your IP address from the hardlock server and configure this 
    IP address in the client machine so that it is compatible with the 
    server's. To do this, you must follow these instructions in the 
    client machine: Edit the TCP/IP protocol configuration from: My PC 
    > Control Panel > Network. It is possible that in the list of 
    network elements there is more than one TCP/IP protocol if the 
    machine has telephone access to networks, or has more than one 
    network card. Select the TCP/IP protocol corresponding to the 
    network card that you wish to configure and click on: Properties. 
    A dialogue with various tabs will open. Click on the 'IP address' 
    tab. Here select the option: Specify an IP address. Type in an IP 
    address compatible with the hardlock server's IP address. Two IP 
    addresses are compatible when, having the same sub-network masks, 
    the numbers change only in a 0 sub-network mask. For example, if 
    the sub-network mask is: 225.225.225.0, the IP addresses 
    192.168.0.1 and 192.168.0.2 will be compatible. In more complex 
    networks, there may be sub-network masks in which one of the 
    numbers is neither 255 nor 0, but this is not common. 
   -In the case that you can see the hardware lock server, there might 
    be a problem with the port. Make sure that the hardlock server and 
    the client programs are using the same port. To do this, click on 
    the 'Advanced configuration' in the hardlock server, consult the 
    'Server port' and 'Locating port' values, write them down and 
    check that the client machines have the same values in the 
    'Network hardware lock configuration' window. If upon placing the 
    same values for the ports, the hardlock is still not detected, 
    there might be a router or firewall inside the network that 
    prevents the connection. To solve this, change the value of the 
    ports in all the machines in the network that are clients of the 
    hardlock and in the server (place the same value in all). 
   -Finally, if this also fails, the configuration of the router or 
    the firewall must be changed. 
  
CASE 3. Novell Networks 

 The network hardware lock does not work in the Novell server. This 
  happens because the hardlock server is a win32 application and it 
  must be executed in a Windows operating system. In any case, you can 
  make the hardlock server work in one of the Novell network clients 
  as long as this machine, along with the rest of the machines where 
  you wish to install the program, work with Windows and have the 
  TCP/IP protocol installed. 

  
CYPE 
